@dankcushions I don't think I've done any config changes related to the functionality of the hotkey combo.
If you start a game using Mame 2003 and press F4 (show gfx) then you get the screen I showed in my first post. I tested it just now and the hotkey combination to exit doesn't work.

Well found another bug not sure when this one crept in but the midway games need fixed again as this was changed during the refactoring.

its broke in plus as well with if you turn off bypass audio skew.

unfortunately the bypass audio skew needs fixed in mame2003 and its off by default. Since you are syncing the cores ill let you decide what you want to do with it.

@GreenHawk84 - I think the vector code for mame2003 and mame2003-plus are pretty much identical now.

One thing that has changed is instead of a vector resolution multiplier of 1, 2, 3, etc. it will be the actual render resolution under the Quick Menu -> Options settings.

If one of the core resolutions match the native native resolution of your monitor it should like decent. If you can't match the resolution to the display exactly then shoot for something close. I find using an HD display (1920x1080) that 1440x1080 looks decent for both horizontal and vertical vector games.

Try a vector beam width of 1 or 1.2 (Quick Menu -> Options) and if it still doesn't look satisfactory try turning on bi-linear filtering under Settings -> Video.

Some of the options require a core restart, basically exit the game and restart it.

@Run-the-Jewels If you have the Pimoroni controller (X Hat) then you should do what I did, see above. Some additional information is on the Pimoroni forums, see https://forums.pimoroni.com/t/x-hat-retropie-coin-button-exits-game/9633.

If you have another controller, then this might not be the same problem. If this is the case, then I suggest you start a new thread, with detailed descriptions of your hardware, software versions, log file entries etc.

@BuZz said in MAME 2003 "vector" games only displaying 1/4 of screen after updating - what needs to be edited?:

BTW the vector games did work on the last binary so it may have been a core option affecting this. there has been some fixes since then though including some relating to the new vector code and the settings, but the last binary is not "old" (It's from the 11th October). I will update the binary though.

Thank you @BuZz if there are still problems with vectors in mame2003 after this binary update I will work to resolve them.

@tuntav This may be information you already know, but both mine are detect as mice and the spinner overrides the mouse. The only way I get around is to find out what device number each mouse is (spinner is detected as mouse) and then start game, go into retroarch and set the mouse input to the number assigned to what mouse I want to use and then save the game settings (not the core settings).

For example, my spinner is device 0 and mouse is device 2. For a game like Centipede, I just go into Retroarch, set Mouse Input from 0 to 2 and save the game config so only affects that game.

Have done the same for AdvanceMame, but that does not use Retroarch but a config file.

Again, you may already know this, so I am sorry if I am repeating information you already know.

the problem was that your foundation was wrong i think.

my theory: during https://retropie.org.uk/docs/First-Installation/#configure-controllers you bound L bottom/R bottom to your L and R buttons. you should have bound L top and R top. this would probably mean that MK would have had sensible default controls (along with SF2, etc), and it would have also meant that you had no SNES button bound to the MAME menu (not that you should need access to it anyway).

@dankcushions I did try with MAME2003plus and Operation thunderbolt and the issue persisted, don't know if other games are fixed.

@grant2258 This worked. Thank you.

@dankcushions Thanks, many handy things on that page!

@urko948 The roms / zip files shouldn't be renamed. Mame expects them with specific names, because in the emulator is a database of filenames and other informations. Thats why you need a specific romset for a specific Mame version btw. If you rename anything, then you should do this within the gamelist.xml or elsewhere related. So, you should bring back the original state of roms with original names. Then remove the non working gamelist.xml by moving the file to different place for later analysis.

And then? I don't know. :D Maybe upload the faulty gamelist.xml, so we can check it and maybe see something unusual going on.

@mitu Thank, that makes sense. I had looked through that link previously multiple times, but not found anything saying that “input_12_btn” didn’t work. I will post my configs tomorrow, and manually modify the cfg file to see what happens. If I can confirm that the “input_12_btn” is being created instead of right trigger or whatever, I will report it as a bug

@markwkidd this has all been a team effort its so much better no we can work together with libretro

I know this topic is old, but I was having a problem with building this as well recently. Basically the same error. Resolution was to disconnect all controllers (I had 5 plus keyboard plugged in.) Confirmed this as the solution in my case, and adding it here in case others experience it.

@m0riarty Better response might be from the better performance of the emulator tested. MAME4ALL is based on an old mame version is no longer developed, things have improved over time.
If you wish to investigate more, head on over to the docs and you can see all the available arcade emulators on RetroPie - https://retropie.org.uk/docs/Arcade/

@baviaannl Maybe the youngster came back and re-mapped the buttons by mistake :).

@scopaust said in 0.78 Romset Retropie Black Screen:

One more question, how do I know what bios is required by a MAME2003 game

You could use a ROM manager like Romcenter to see the ROM details or look in the compatibility list (https://docs.google.com/spreadsheets/d/1LP1MELCvcxu7TfiowF_0ZuvRVEMqlfQyTVetnOJvuJc/edit?usp=sharing).